System and method for auditing a communications bill

ABSTRACT

A computer-assisted system and method for auditing a communications bill wherein billing information is collected, reformatted and stored for use in a set of automated audits. The system and method for auditing a communications bill further collects data from other external systems such as a work order system, a trouble ticket system, an inventory system, an AMA/SMDR data source, an SS7 event record data source, or another source of call records or billing records. The data collected is used in a set of automated audits to determine if the communications bills contain errors. The system and method will further perform historical audits, and generate and manage the billing dispute process. The system and method will further provide audit reports and interface to an accounts payable system.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority based upon applicants' co-pending provisional patent application U.S. Ser. No. 60/493,752, filed on Aug. 8, 2003.

FIELD OF THE INVENTION

The present invention relates to a system and method for analyzing a communications bill, and more specifically, to a system and method for determining whether a communications bill contains errors that, if identified, would result in a refund and ongoing cost savings to the organization being billed by the communications service provider.

The current state of the Telecommunications business, combined with the complexities of voice and data services, has created an environment where a typical enterprise receives a multitude of complex bills, many of which contain errors. These errors are the result of the massive changes that the communications industry has undergone, and the increased complexity of services that are purchased by an enterprise. This problem is compounded by the need for many communications service providers to utilize incomprehensible and complicated pricing schemes as a form of marketing.

Enterprises are aware of these billing problems, and typically will manually review and validate their invoices on a periodic basis. Many large Enterprises perform audits of their telecom invoices manually or through consultants. These audits are typically performed quarterly or annually, and are very labor intensive. The audits are either performed in house or through a consulting contract that typically pays the consultant for successful disputes. The ability to perform a successful audit of an enterprise's communications bills is based on experience. The skilled auditors know the areas of a communications bill that are prone to errors, and further have specific knowledge of which communications vendors have certain billing problems. The skilled auditors primarily work for consulting firms that specialize in communications billing audits. The skilled auditors are typically not willing to share their knowledge and expertise with others due to the contingent nature of their business. Most auditors work on a contingency fee basis where they are paid a percentage of the savings which they identify. A 30-50% contingency fee is very typical, and can result in a very large fee that the consultant receives. An automated software system and method would be counterintuitive to their business model; and as such, such a computer based system and method has not been proposed in the field.

The results of a typical audit reveal numerous overcharges and billing errors. Large enterprises spend millions of dollars per year on communications services. The ability to detect and correct billing errors has a direct impact on the organization's financial statements. For example, a mid sized enterprise that spends 3 Million dollars a year on communications services can typically find a 5-10% error rate on their bills. These errors, when identified, are returned to the organization for the period of time that they have been occurring. Often times finding these errors can have a significant positive impact on the organization's financial condition.

There is currently no automated way to detect these billing errors, track their recovery, and generate audits and reports to ensure that the bills that are paid are error free. These audits are performed manually, and are very labor intensive and costly to undertake. There are software products on the market today that are designed for Invoice Processing, but no software products that are designed specifically to automate the audit process. The current state of Invoice Processing software products are designed to read in an invoice electronically, and to process that invoice in a format that can be sent electronically to an accounts payable system. Such products include Telesoft's IPS (Invoice Processing Software) and TTI's WinBill. These products are designed for Invoice processing and bill tracking, and do not address the need to specifically audit and detect billing errors.

United States Patent Application Publication US2004/0078330 entitled METHOD AND APPARATUS FOR AUDITING BILLING ACCOUNTS describes a method and apparatus for analyzing client bills from individual service providers such as attorneys to detect fraud by removing confidential information from the bill and validating the accuracy of the bill. The Method and Apparatus disclosed in patent application publication US2004/0078330 does not audit communications bills from communications providers such as carriers, and as such, does not contain the audits or data collection and processing techniques required to audit a communications bill and the complexities associated with communications billing.

United States Patent Application Publication US2003/0036918 A1 entitled SYSTEM AND METHOD FOR TRUSTED SELF-BILLING AND PAYMENT FOR UTILITIES INCLUDING AUDIT, VERIFICATION, RECONCILIATION AND DISPUTE RESOLUTION describes a system for validating service bills using two monitoring subsystems to independently measure the services received and assign a cost to those services using one monitoring subsystem, and using a second monitoring subsystem to collect the billing information from the service provider. The system and method described in this patent application publication is concerned with auditing and verifying usage only. It does not consider other information that may be contained in the bill such as recurring charges, taxes and credits, past due amounts, and the like. Further, the system described monitors usage on a per line basis, and contains a rating or costing algorithm to assign a cost. Such a “per line” monitoring device is impractical for large enterprises that may utilize thousands or tens of thousands of lines and circuits in a multiplexed T1 or T3 configuration. In addition, communications billing and rating are highly complex, and require a fairly high level of skill and cost to be performed properly. Such an undertaking would be cost prohibitive on a per line basis, as disclosed in said patent application publication. It is thus desirable to audit, verify and reconcile billing information on a larger scale such as encountered in a corporation or governmental organization without the need to physically monitor each phone line. It is further desirable to audit communications bills in areas other than usage by using information from other systems such as trouble ticket systems, work order systems, inventory systems, Signalling System Number 7 systems, Automatic Message Accounting Systems, Station Message Detail Recording systems, and the like.

SUMMARY OF THE INVENTION

According to one embodiment of the invention, a system and method for auditing a communications bill is provided. The system generally includes an audits and error detection module, and electronic billing data information retrieval unit, a manual entry billing data information retrieval unit, at least one billing data interface module, and an audit report generation module.

In another embodiment of the invention, the system for auditing a communications bill includes a call detail record data collection unit and further contains software to match the call detail records to the communications billing data to identify errors in the communications bill. Call detail records may include station message detail records, automatic message accounting records, internet protocol detail records, cellular call detail records, event records, and the like.

Another embodiment of the invention includes a Signaling System Number 7 (SS7) event message record data collections unit and further contains software to match the SS7 event message records to the communications billing data to identify errors in the communications bill.

Still another embodiment of the invention further contains a trouble ticket data information retrieval unit and software to audit the communications billing data against the information contained in the trouble ticket data to identify possible billing errors. One such example of a billing error that could be identified with the use of trouble ticket data is incorrect billing for a service outage when a credit for the outage should have been issued on the communications bill.

Still another embodiment of the invention further contains a work order data information retrieval unit and software to audit the communications billing data against the information contained in the work order data to identify possible billing errors. One such example of a billing error that could be identified with the use of work order data is continued billing for communications services after a work order was issued to disconnect the communications service. Another example of a billing error that would be identified by an embodiment of the invention is a premature start of billing prior to the completion of a work order to initiate service.

Yet another embodiment of the invention further contains contains an inventory data information retrieval unit and software to audit the communications billing data against the information contained in the inventory data to identify possible billing errors. One such example of a billing error that could be identified with the use of inventory data is a billing charge for an item or a service that does not belong to the billed party.

In some embodiments the results of the automated audits are used by a dispute processing module. The dispute processing module may include various components of the billing dispute process such as filing the billing dispute with the carrier or billing entity, tracking the billing dispute, short paying the bill, tracking associated late charges, validating that a credit has been issued for the dispute, maintaining records of the dispute dialogue, and the like.

In other embodiments the invention may include an accounts payable interface module that provides validated and audited billing data to an accounts payable system.

Other embodiments may include the ability to store and archive data both in raw form and in a form that is representative of the audit results provided by the audit and error detection module.

Some embodiments of the invention may allow the audit logic contained in the audit and error detection module to be modified by a user.

The invention may also be adapted for use through a web browser or an e-mail system.

In another aspect, the invention comprises a computer assisted method of auditing a communications bill comprising the steps of retrieving billing data information from at least one external input file wherein said at least one external input file contains communications billing information; formatting and storing said billing data information on a data storage device; storing on a computer a set of selectable audit types; selecting one or more selected audit types by inputting appropriate selection data with an input device; performing selected audits using billing data information contained on a data storage device; and automatically generating audit reports based on the selected audit types.

In some embodiments of the invention the steps may include collecting event records such as Station Message Detail Records (SMDR), Automatic Message Accounting (AMA) records, Internet Protocol Detail Records (IPDR), Call Detail Records (CDR) and the like, and comparing said event records to billing data information to identify billing errors. Other embodiments of the invention may include the steps of collecting Signaling System Number 7 (SS7) event message records and comparing said SS7 event message records to billing data information to identify billing errors.

Further embodiments of the invention may include the steps of collecting trouble ticket data and using said trouble ticket data to further identify billing errors. Still another embodiment of the invention may include the steps of collecting work order data and using said work order data to further identify billing errors. Yet another embodiment of the invention may include the steps of collecting inventory data and using said inventory data to further identify billing errors.

Some embodiments of the invention may include the steps of using the audit results to manage the overall dispute process, he dispute process may include steps such as filing the billing dispute with the carrier or billing entity, tracking the billing dispute, short paying the bill, tracking associated late charges, validating that a credit has been issued for the dispute, maintaining records of the dispute dialogue, and the like.

Yet other embodiments of the invention may include the steps of providing the processed billing information and the audit results to an accounts payable system.

Further embodiments of the invention may include the steps of accessing and using the invention through a web browser or an e-mail system.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements and in which:

FIG. 1 is a flowchart of an auditing system and method according to one embodiment of the present invention;

FIG. 2 is a block diagram of a preferred computer system of the invention;

FIG. 3 is a functional block diagram of an auditing system according to one embodiment of the present invention;

FIG. 4 is a functional block diagram of the Signaling System Number 7 (SS7) data matching usage audit according to one embodiment of the present invention;

FIG. 5 is a functional block diagram of the Automatic Message Accounting (AMA) data matching usage audit according to one embodiment of the present invention;

FIG. 6 is a functional block diagram of the Station Message Detail Recording (SMDR) data matching usage audit according to one embodiment of the present invention; and

FIG. 7 is a functional block diagram of the Event Record data matching usage audit according to one embodiment of the present invention.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

A method and apparatus for verifying the accuracy of a communications invoice is described. In the following description, for the purposes of explanation, numerous software functional blocks are described. The present invention may be practiced with all or only some of the functional blocks.

Referring to FIG. 1, communications invoices are received either on paper and entered manually into a computer system in step 102, or electronically on either a media such as a Compact Disc (CD) or via an interface such as Electronic Data Interchange (EDI), in step 104. The billing data is typically in a format that is specific to the vendor providing the bill. For example, AT&T's electronic billing product is known as Billing Edge™, and is provided in a format that is unique to AT&T. Therefore, an interface module 106 is required to process the bill in it's unique format, and read the billing data into a standard format. Once the billing data is read into a standard format in step 106, the data is structured, indexed, formatted and stored in a data structure, such as a data storage and archiving module (DSAM), in step 108.

In performing a comprehensive set of automated audits in the software, information other than billing data is required. This information can be sent electronically to the data structure of step 108 from other systems. These systems can include an inventory system in step 112, a work order system in step 114, and a trouble ticket system in step 116. A source of Automated Message Accounting (AMA) data from a central office switch, Station Message Detail Recording (SMDR) data from a Private Branch Exchange (PBX) in step 117 is also transferred to said data structure in step 108. A source of Signaling System Number Seven (SS7) event records in step 119 may also provide data to the data structure of step 108. The signaling System Number Seven (SS7) event records may be pre-processed and converted to a call detail record, as described in U.S. Pat. No. 6,327,350 entitled “Methods and Systems For Collecting And Processing Signaling System 7 (SS7) Message Signal Units (MSUS), incorporated herein by reference in it's entirety.

Once the data structure in step 108 has been populated by way of steps 106, 112, 114, 116, 117 or 119, a series of automated audits and error detection routines are initiated in step 110. The audits are defined in this specification under the heading AUDIT SET, and are provided to illustrate by example one preferred embodiment of the invention, but are not intended to be limiting.

In step 110, the user may elect to run one, several or all of the audits that are contained in the software. The user may further elect to define a custom audit or modify audit parameters in step 140. If step 110 results in the detection of billing errors at step 120, the dispute process is started at step 122. This dispute process includes identifying the error, the amount of the error, unique identifying data from the invoice, and other attributes that will assist in recovering the amount in question. Once the dispute process is started in step 122, the same error detection routines that found the current billing error are applied to similar historical billing data in step 124 to determine how long this billing error has been occurring. This historical auditing data is used in the overall dispute process, and will be used to generate the total amount of the billing error that is automatically entered on a dispute form in step 126 that may be provided to the billing vendor. In step 128, the disputed amount is tracked, and compared to credits received on future bills. Additionally, late payment charges and other charges and credits that may impact the disputed amount are tracked in step 128. Upon completion of step 128, the invoice is formatted to allow receipt by the accounts payable system in step 130. Once the formatting is completed in step 130, the invoice is sent to the accounts payable system for approval and payment.

Returing to step 120, if no billing errors are identified, the invoice is formatted to allow receipt by the accounts payable system in step 130. Once the formatting is completed in step 130, the invoice is sent to the accounts payable system for approval and payment in step 132.

The invention also provides a set of reports in step 118 that are useful in managing billing information and tracking billing errors. These reports are generated from the data stored in the data storage and archiving module (DSAM) in step 108, or can be generated using data from the audits and error detection module in step 110. These reports follow standard accounting practices, and can be modified, created or changed by a user of the invention.

The invention may further generate an e-mail notification in step 150 if certain audit conditions are met. The e-mail may alert the designated recipient that certain audit thresholds have been exceeded, or may contain audit reports or hyperlinks to audit reports.

Referring now to FIG. 2, a block diagram of a preferred computer system of the invention is shown. The various software modules, software components and software units, as will be further described using FIG. 3, are contained in computer system 210. The computer system 210 is connected to a network 230 to allow for the use of the invention through other computer systems 250. Said network 230 may be a Virtual private network, an Ethernet network, a wireless network, the internet, a corporate intranet, or the like. The computer system 210 will read data from external systems and files 220 that contain billing data, inventory system data, work order system data, trouble ticket system data, Automatic Message Accounting Data (AMA), Station Message Detail Recording Data (SMDR), Signaling System Number 7 Data, Event Record Data, cellular call detail records, or manual billing data. Said computer system 210 further provides outputs 240 in the form of audit reports, web based reports, dispute forms, accounts payable files and e-mail audit alerts.

Referring now to FIG. 3 a functional block diagram of an auditing system according to one embodiment of the present invention is shown. A data information retrieval module (DIRM) 310 is shown. This software component contains various data information retrieval units (DIRUs). A data information retrieval unit (DIRU) is a means for transferring data from an external source to the system for auditing a communications bill. The data information retrieval module provides access and file transfer capabilities for the various raw inputs required for the invention. The data information retrieval module 310 collects the raw data files that contain billing data, inventory data, work order data, trouble ticket data, automatic message accounting (AMA) data, station message detail recording (SMDR) data, Signaling System Number 7 (SS7) data and event record data that may include cellular call detail records. The data information retrieval module 310 is comprised of an electronic billing data information retrieval unit 301 that functions to collect raw electronic billing data files, a manual billing data information retrieval unit 302 that functions to collect raw manual billing data files, an inventory system data information retrieval unit 303 that functions to collect raw inventory system data files, a work order data information retrieval unit 304 that functions to collect raw work order system data files, a trouble ticket data information retrieval unit 305 that functions to collect raw trouble ticket system data files, an AMA/SMDR data information retrieval unit 306 that functions to collect raw automated message accounting and station message detail recording system data files, a Signaling System Number 7 (SS7) record data information retrieval unit 307 that functions to collect raw signaling system number 7 data files, and an event record data information retrieval unit 304 that functions to collect raw event record data files.

Operatively coupled to said Data Information Retrieval Module (DIRM) 310 is the interface and formatting module (IFM) 320 that serves to process and filter the raw data collected by each information retrieval unit using formatting and processing logic that is specific to each information retrieval unit. The interface and formatting module 320 provides data in a format that can be used to perform audits and error detection. Extraneous information that may be included in the raw data is stripped and only specified date range, account numbers, and billing identifiers are kept. The interface and formatting module 320 provides data that can be used by the audit and error detection module (AEDM) 110. Said audit and error detection module (AEDM) 110 contains the algorithms necessary to perform the audits. The audits contained in the audits and error detection module (AEDM) 110 include a series of general audits, a series of other charges and credits (OC&C) audits, a series of facilities audits, and a series of usage audits. The specific audits that are contained in each of these categories are defined below.

General Audits

The General Audits perform an audit of the existence of a charge on an invoice using the audit control thresholds set by the user.

Invoice Audits

The Invoice Audit verifies that the total amount that was billed for the invoice summary is equal to the detail records of the invoice.

Late Invoice Audits

The Late Invoice Audit will determine if a monthly invoice has not been received on time to avoid late payment charges. If a monthly invoice is not received within ‘X’ number of days after the invoice date, the data storage and archiving module (DSAM) will create a Late Invoice record for that invoice and alert the user to the fact that the expected invoice has not arrived.

Late Payment Audit

The Late Payment Audit will automatically flag all Late Payment charges that are billed, giving the auditor the opportunity to verify the charges and either dispute or decline a dispute using the dispute processing module (DPM) 350.

OC&C Audit

The OC&C (Other Charges and Credits) Audit will automatically flag any charges that are billed as Other Charges and Credits, giving the auditor the opportunity to verify the charges and either dispute or decline a dispute using the dispute processing module (DPM) 350.

MRC Audit

The MRC (Monthly Recurring Charges) Audit automatically flags any charges billed as Monthly Recurring Charges, giving the auditor the opportunity to verify the charges and either dispute or decline a dispute using the dispute processing module (DPM) 350.

Taxes Audit

The Tax Audit automatically flags any charges that are billed taxes, giving the auditor the opportunity to either dispute or decline a dispute. TABLE 1 Taxes LOCAL LONG DISTANCE Federal Excise Tax Federal Excise Tax State and Local Taxes State and Local Taxes Foreign State and Local Tax-Calling Card Surcharges Audit

The Surcharges Audit automatically flags any surcharges that are billed, giving the auditor the opportunity to either dispute or decline a dispute using the dispute processing module (DPM) 350. TABLE 2 Surcharges LOCAL LONG DISTANCE LNP Fee Federal, State and Local Surcharge Network Access Charge Foreign State and Local Surcharge-Calling Card State and Local Surcharge Federal Universal Service Fee Payphone Access Fee Balancing to Total Amount Due Audit

The Balancing to Total Amount Due Audit keeps track of all past balances whether they are payments or disputes outstanding.

General Ledger Code Assignment Audit

The General Ledger Code Assignment Audit verifies whether all charges on a bill have a GL assignment.

Facility Inventory Audits

The Facility Inventory Audits verify Universal Service Order Code (USOC)/feature consistency for each component of the charges for a given circuit location. The Facility Audits include Universal Service Order Code, Quantity, Effective Date, Disconnect Date, Rate, Facilities Billed vs. Facilities in inventory system.

Multiple Bills Audits

The Multiple Bills Audits verify only one invoice is paid using billing date and billing account number.

Valid Billing Account Record Audits

The Valid Billing Account Record Audits verify if the invoice received is a valid invoice for you. The Valid Billing Account Record Audits include billing account number, date, bill cycle date, bill period, and company name

Inactive Account Audit

The Inactive Account Audit verifies if the account is inactive or not correct.

SMDR Summary Audit

The SMDR Summary Audit verifies whether the SMDR data has been received prior to running the usage audits.

Trunk Charge Audit

The Trunk Charge audits validate the accuracy of trunk charges received on the invoice by comparing actual charges to expected charges.

OC&C Debit Audits

The OC&C Debit Audits verify the non-recurring charges and the fractional monthly recurring charges on an invoice.

OC&C NRC Circuit Existence Audits

The NRC Circuit Existence Audits validate that the circuit where the one-time charges are being assessed exists for the Billing Account Number (BAN). These audits compare the circuits being billed against the circuits listed in the Facility Circuit Inventory. Using the circuit ID, the audit detects any inconsistencies between the invoice and the inventory. Inconsistencies occur when a circuit is not listed in the Facility Circuit Inventory or when a circuit is listed as invalid. The OC&C NRC Circuit Existence Audits are performed on the effective date and the disconnect date.

OC&C NRC Service Establish Date Audit

The NRC SED (Service Established Date) audit compares the Work Order Completion Date with the Service Establish Date for the circuit to determine whether the charges are disputable. This audit calculates the difference between the Work Order Completion Date and the Service Establish Date to ensure that the inventory item was in service for the billing period being invoiced. If this audit identifies a discrepancy, it disputes the entire amount being billed. The information used for this audit is from the work order system.

OC&C NRC Rate Audits

The NRC Rate Audits verify the non-recurring charge by using known rates, calculating the appropriate non-recurring charge, and comparing it to the invoiced amount.

OC&C Fractional Circuit Existence Audits

The Fractional Circuit Existence Audits validate that the inventory item where the charges are being assessed exist for the Billing Account Number (BAN). These audits compare the circuits being billed against the circuits listed in the Facility Circuit Inventory. Using the circuit ID, the audit detects any inconsistencies between the invoice and the inventory. Inconsistencies occur when a circuit is not listed in the Facility Circuit Inventory or when a circuit is listed invalid. The OC&C Fractional Circuit Existence Audits are performed by effective date and disconnect date.

OC&C Fractional Service Establish Date Audit

The Fractional Service Establish Date (SED) Audit compares the Work Order Completion Date with the SED for the inventory item to determine whether the charges are disputable. This audit calculates the difference between the SO Completion Date and the SED to ensure that the inventory item was in service for the billing period being invoiced.

OC&C Fractional Feature Audits

The Fractional Feature Audits confirm that the inventory item where the charges are being assessed is valid for the circuit. These audits also check the quantity being billed by comparing the quantity billed to the actual quantity in the Facility Circuit Inventory for the selected BAN, circuit, location, and USOC. Inconsistencies occur when a feature is not listed in the facility Circuit Features Inventory, when feature values are different, or when a feature is listed as invalid. If a feature is not valid for the dates being billed, the system identifies the feature as invalid, then calculates and disputes the fractional amount being billed for the feature. The Facility Features Audit runs after the Facility Circuit existence Audit, so any disputed circuits will not be included in the facility Features Audit.

OC&C Fractional Rate Audits

The Fractional Rate Audits looks up the monthly recurring rate in the Facility Rate Maintenance tables and determine a per-day rate. The audits then multiply the per-day rate by the number of days to recalculate the actual fractional amount, and compares it with the invoiced amount. When the system identifies an overbilling discrepancy, it labels the record as a dispute.

Facility Audits

Facility Audits compare electronic or manual invoices against a circuit and Universal Service order code (USOC) inventory and against industry rate and tariff information. Business rules can be established by the user of the software to determine the threshold for flagging an item as disputed.

Facility Circuit Existence Audits

The Facility Circuit Existence Audits compare the circuits being billed against the circuits listed in the Facility Circuit Inventory. Using the circuit ID, this audit detects any inconsistencies between the invoice and the inventory. Inconsistencies occur when a circuit is not listed in the Facility Circuit Inventory or when a circuit is listed as invalid.

Facility Features Audits

The Facility Features Audits compare the features (USOCs) being billed against the features listed in the Facility Circuit Inventory for the same BAN, circuit, location, and USOC. The Facility Features Audits run after the Facility Circuit Existence Audit, so any disputed circuits will not be included in the facility Features Audits.

In addition, features that the Facility Features Audits identify as disputable and also have a rate discrepancy will appear in the Facility Audits results as Facility Rate Audit disputes. Disputes can only be counted under one category and the Facility Rate Audits are the last to be run, so items with both a feature and a rate dispute will appear in Facility Audit results as a Facility Rate Audit.

The Features Audits also check the quantity of features being billed by comparing the quantity billed to the actual quantity in the Facility Circuit Features Inventory table for the selected BAN, circuit, location, and USOC. Inconsistencies occur when a feature is not listed in the Facility Circuit Features Inventory or when a feature is listed as invalid. The feature must be valid for the dates being billed or the system identifies the feature as invalid and disputes the entire amount being billed for the feature.

Facility Rate Audits

The Facility Rate Audits compare the rates being billed against rates being stored. The Facility Rate Audits run after the Facility Circuit Existence Audits and Facility Features Audits. Any circuits that were disputed in the Facility Circuit Existence Audits will not be included in the Facility Rate Audits.

The Rate Audits deal only with discrepancies that are rate-based. This means that any other dispute characteristics (such as rate zone and jurisdiction) are dealt with in the Facility Features Audits.

In addition, features that the Facility Features Audits identify as disputable and also have a rate discrepancy will appear in the Facility Audit Results as Facility Rate Audit disputes. Disputes can only be counted under one category and the Facility Rate Audit is the last audit to be run, so items with both a feature and a rate dispute will appear in Facility Audit Results as a Facility Rate Audit.

SMDR Usage Audits

The Usage Audits verify Minutes of Use (MOU), Percentage of Interstate Usage (PIU), 800 Charges, and Directory Assistance (DA). The Usage Audits also include Rate Audits, which verify billed rates.

Minutes of Use Usage Audits

The Minutes of Use (MOU) Usage Audits verify the billed Minutes of Use (MOU) against the summarized SMDR data. MINUTES OF USE (MOU) Audits are performed for both current and backbilling cycles.

Total Long Distance MINUTES OF USE (MOU) Audits

The total long distance Minutes of Usage Audits verify the billed long distance MINUTES OF USE (MOU) against the long distance SMDR data. Audits are performed for both current and backbilling cycles.

Total Local Measured Service Audits

The total local measured service Audits verify the billed local calls against the local SMDR data. Audits are performed for both current and backbilling cycles.

Total International MINUTES OF USE (MOU) by Country Code Audits

The total International Minutes of Usage Audits verify the billed International Minutes of Use (MOU) against the International SMDR data. Audits are performed for both current and backbilling cycles.

800 Charge Audits

The 800 charge audits validate the charges applied for an 800 number by using rate and usage information stored in the data storage and archiving module (DSAM).

Directory Assistance Audits

The Directory Assistance Audits audit the billed quantity of Directory Assistance (DA) calls and attempts against the actual number of DA calls.

Rate Audits

The Rate Audits verify that billed rates for a given rate element do not exceed the tariffed or user-supplied rates. Usage rates are validated for each rate variable against the tariff or contract rates. The data storage and archiving module (DSAM) can be populated manually for contract and/or interconnection agreement rates or by using a tariff rate vendor.

AMA Usage Audits

The Usage Audits verify Minutes of Use (MOU), Percentage of Interstate Usage (PIU), 800 Charges, and Directory Assistance (DA). The Usage Audits also include Rate Audits, which verify billed rates.

Minutes of Use Usage Audits

The Minutes of Use (MOU) Usage Audits verify the billed Minutes of Use (MOU) against the summarized AMA data. Minutes of Use (MOU) Audits are performed for both current and backbilling cycles.

Total Long Distance Minutes of Use (MOU) Audits

The total long distance Minutes of Usage Audits verify the billed long distance Minutes of Use (MOU) against the long distance AMA data. Audits are performed for both current and backbilling cycles.

Total Local Measured Service Audits

The total local measured service Audits verify the billed local calls against the local AMA data. Audits are performed for both current and backbilling cycles.

Total International MINUTES OF USE (MOU) by Country Code Audits

The total International Minutes of Usage Audits verify the billed International Minutes of Use (MOU) against the International AMA data. Audits are performed for both current and backbilling cycles.

800 Charge Audits

The 800 charge audits validate the charges applied for an 800 number by using rate and usage information stored in the data storage and archiving module (DSAM).

Directory Assistance Audits

The Directory Assistance Audits audit the billed quantity of Directory Assistance (DA) calls and attempts against the actual number of DA calls.

Rate Audits

The Rate Audits verify that billed rates for a given rate element do not exceed the tariffed or user-supplied rates. Usage rates are validated for each rate variable against the tariff or contract rates. The data storage and archiving module (DSAM) can be populated manually for contract and/or interconnection agreement rates or by using a tariff rate vendor.

Event Record Usage Audits

The Usage Audits verify Minutes of Use (MOU), Percentage of Interstate Usage (PIU), 800 Charges, and Directory Assistance (DA). The Usage Audits also include Rate Audits, which verify billed rates.

Minutes of Use Usage Audits

The Minutes of Use (MOU) Usage Audits verify the billed Minutes of Use (MOU) against the summarized event record data. Minutes of Use (MOU) Audits are performed for both current and backbilling cycles.

Total Long Distance Minutes of Use (MOU) Audits

The total long distance Minutes of Usage Audits verify the billed long distance MINUTES OF USE (MOU) against the long distance event record data. Audits are performed for both current and backbilling cycles.

Total Local Measured service Audits

The total local measured service Audits verify the billed local calls against the local event record data. Audits are performed for both current and backbilling cycles.

Total International Minutes of Use (MOU) by Country Code Audits

The total International Minutes of Usage Audits verify the billed International Minutes of Use (MOU) against the International event record data. Audits are performed for both current and backbilling cycles.

800 Charge Audits

The 800 charge audits validate the charges applied for an 800 number by using rate and usage information stored in the data storage and archiving module (DSAM).

Directory Assistance Audits

The Directory Assistance Audits audit the billed quantity of Directory Assistance (DA) calls and attempts against the actual number of DA calls.

Rate Audits

The Rate Audits verify that billed rates for a given rate element do not exceed the tariffed or user-supplied rates. Usage rates are validated for each rate variable against the tariff or contract rates. The data storage and archiving module (DSAM) can be populated manually for contract and/or interconnection agreement rates or by using a tariff rate vendor.

SS7 Usage Audits

The Usage Audits verify Minutes of Use (MOU), Percentage of Interstate Usage (PIU), 800 Charges, and Directory Assistance (DA). The Usage Audits also include Rate Audits, which verify billed rates.

Minutes of Use Usage Audits

The Minutes of Use (MOU) Usage Audits verify the billed Minutes of Use (MOU) against the summarized SS7 data. Minutes of Use (MOU) audits are performed for both current and backbilling cycles.

Total Long Distance Minutes of Use (MOU) Audits

The total long distance Minutes of Usage Audits verify the billed long distance Minutes of Use (MOU) against the long distance SS7 data. Audits are performed for both current and backbilling cycles.

Total Local Measured Service Audits

The total local measured service Audits verify the billed local calls against the local SS7 data. Audits are performed for both current and backbilling cycles.

Total International Minutes of Use (MOU) by Country Code Audits

The total International Minutes of Usage Audits verify the billed International Minutes of Use (MOU) against the International SS7 data. Audits are performed for both current and backbilling cycles.

800 Charge Audits

The 800 charge audits validate the charges applied for an 800 number by using rate and usage information stored in the data storage and archiving module (DSAM).

Directory Assistance Audits

The Directory Assistance Audits audit the billed quantity of Directory Assistance (DA) calls and attempts against the actual number of DA calls.

Rate Audits

The Rate Audits verify that billed rates for a given rate element do not exceed the tariffed or user-supplied rates. Usage rates are validated for each rate variable against the tariff or contract rates. The data storage and archiving module (DSAM) can be populated manually for contract and/or interconnection agreement rates or by using a tariff rate vendor.

Again referring to FIG. 3, the data storage and archiving module (DSAM) 330 may utilize a database, an alternate data structure, or a series of files to store the raw data collected by the information retrieval units of the data information retrieval module (DIRM) 310, the data that has been processed by the interface and formatting module (EFM) 320, and the audit results from the audit and error detection module (AEDM) 110. A relational database is one preferred architecture for said data storage and archiving module (DSAM) 330. Examples of relational databases include Oracle TM, Sybase TM, and Microsoft Access TM. The audit report generation module (ARGM) 340 accesses data contained in the data storage and archiving module (DSAM) 330 for formatting and compilation into a set of audit reports 381. The audit report generation module (ARGM) 340 will generate reports in printable or electronic format. The audit reports 381 may be modified by a user. An electronic audit report may be further customized using an ad hoc report writer such as Crystal Reports TM by Crystal Decisions, Inc. The audit reports 381 may further be provided using web based reporting 382 such that the reports can be accessed using hyperlinks from a web site. Electronic format audit reports may be stored in the data storage and archiving module (DSAM) 330 for future use.

The dispute processing module (DPM) 350 contains the logic necessary to execute and track the dispute process, as defined in FIG. 1, steps 122, 124, 126, 128, 130 and 132. The dispute processing module (DPM) 350 also generates dispute forms 383 to be used in the dispute process.

Referring again to FIG. 3, an accounts payable interface module 384 receives audited billing information from the audit and error detection module (AEDM) 110 and formats the billing information so that it can be read and processed by an accounts payable system. Examples of accounts payable systems include SAP™, PeopleSoft™ and Oracle Financials™. The accounts payable interface module 384 may further receive information from the dispute processing module (DPM) 350 indicative of any disputes, credits, debits or short pays that have occurred.

FIG. 3 also illustrates e-mail alerts 385. The e-mail alerts 385 automatically sends e-mail to designated e-mail addresses that contains audit information or hyperlinks to said audit information.

Referring now to FIG. 4, a functional block diagram of the Signaling System Number 7 (SS7) data matching usage audit is shown. Signaling System Number 7 (SS7) data 410, having been collected by the SS7 record data information retrieval unit 307 (FIG. 3) in the data information retrieval module 310 (FIG. 3), and processed through the interface and formatting module (IFM) 320 (FIG. 3), is compared to billing data 420 that has been collected by the electronic billing data retrieval unit 301 (FIG. 3) in the data information retrieval module 310 (FIG. 3), and processed through the interface and formatting module (IFM) 320 (FIG. 3). The signaling System Number Seven (SS7) event records may be pre-processed and converted to a call detail record, as described in U.S. Pat. No. 6,327,350 entitled “Methods and Systems for Collecting and Processing Signaling System 7 (SS7) Message Signal Units (MSUS), incorporated herein by reference in it's entirety.

The comparison of Signaling System Number 7 (SS7) data 410 and Billing Data 420 is performed using the data matching usage audit 430. The Usage audit compares the signaling system number 7 (SS7) data 410 to the billing data 420 to look for errors in total billed minutes of use, total long distance minutes of use, total local measure service, total international minutes of use, total 800 charges, total directory assistance charges, and rates. Upon completion of the data matching usage audit 430, audit reports 381 are generated that contain the specific errors in each of the usage audit categories (total billed minutes of use, total long distance minutes of use, total local measure service, total international minutes of use, total 800 charges, total directory assistance charges, rates and the like). The errors that are identified during the data matching usage audit 430 may further be sent to the dispute processing module (DPM) 350 for dispute actions such as notification, short pay, and the like.

Referring now to FIG. 5, a functional block diagram of the Automatic Message Accounting (AMA) data matching usage audit is shown. Automatic Message Accounting (AMA) data 510, having been collected by the AMA/SMDR record data information retrieval unit 306 (FIG. 3) in the data information retrieval module 310 (FIG. 3), and processed through the interface and formatting module (IFM) 320 (FIG. 3), is compared to billing data 420 that has been collected by the electronic billing data retrieval unit 301 (FIG. 3) in the data information retrieval module 310 (FIG. 3), and processed through the interface and formatting module (IFM) 320 (FIG. 3). This comparison of Automatic Message Accounting (AMA) Data 510 and Billing Data 420 is performed using the data matching usage audit 430. The data matching usage audit 430 compares the Automatic Message Accounting (AMA) data 510 to the billing data 420 to look for errors in total billed minutes of use, total long distance minutes of use, total local measure service, total international minutes of use, total 800 charges, total directory assistance charges, and rates. Upon completion of the data matching usage audit 430, audit reports 381 are generated that contain the specific errors in each of the usage audit categories (total billed minutes of use, total long distance minutes of use, total local measure service, total international minutes of use, total 800 charges, total directory assistance charges, and rates). The errors that are identified during the data matching usage audit 430 may further be sent to the dispute processing module (DPM) 350 for dispute actions such as notification, short pay, and the like.

Referring now to FIG. 6, a functional block diagram of the Station Message Detail Recording (SMDR) data matching usage audit is shown. Station Message Detail Recording (SMDR) data 610, having been collected by the AMA/SMDR record data information retrieval unit 306 (FIG. 3) in the data information retrieval module 310 (FIG. 3), and processed through the interface and formatting module (IFM) 320 (FIG. 3), is compared to billing data 420 that has been collected by the electronic billing data retrieval unit 301 (FIG. 3) in the data information retrieval module 310 (FIG. 3), and processed through the interface and formatting module (IFM) 320 (FIG. 3). This comparison of Station Message Detail Recording (SMDR) Data 610 and Billing Data 420 is performed using the data matching usage audit 430. The data matching usage audit 430 compares the Station Message Detail Recording (SMDR) data 610 to the billing data 420 to look for errors in total billed minutes of use, total long distance minutes of use, total local measure service, total international minutes of use, total 800 charges, total directory assistance charges, and rates. Upon completion of the data matching usage audit 430, audit reports 381 are generated that contain the specific errors in each of the usage audit categories (total billed minutes of use, total long distance minutes of use, total local measure service, total international minutes of use, total 800 charges, total directory assistance charges, and rates). The errors that are identified during the data matching usage audit 430 may further be sent to the dispute processing module (DPM) 350 for dispute actions such as notification, short pay, and the like.

Referring now to FIG. 7, a functional block diagram of the Event Record data matching usage audit is shown. Event Record data 710 includes any billing related record such as a cellular call detail record, an internet protocol call detail record, a packet call detail record, a network call detail record, and the like. Event Record data 710, having been collected by the event record data information retrieval unit 308 (FIG. 3) in the data information retrieval module 310 (FIG. 3), and processed through the interface and formatting module (IFM) 320 (FIG. 3), is compared to billing data 420 that has been collected by the electronic billing data retrieval unit 301 (FIG. 3) in the data information retrieval module 310 (FIG. 3), and processed through the interface and formatting module (IFM) 320 (FIG. 3). This comparison of Event Record Data 710 and Billing Data 420 is performed using the data matching usage audit 430. The data matching usage audit 430 compares the Event Record data 710 to the billing data 420 to look for errors in total billed minutes of use, total long distance minutes of use, total local measure service, total international minutes of use, total 800 charges, total directory assistance charges, and rates. Upon completion of the data matching usage audit 430, audit reports 381 are generated that contain the specific errors in each of the usage audit categories (total billed minutes of use, total long distance minutes of use, total local measure service, total international minutes of use, total 800 charges, total directory assistance charges, and rates). The errors that are identified during the data matching usage audit 430 may further be sent to the dispute processing module (DPM) 350 for dispute actions such as notification, short pay, and the like. 

1. A computer based system for auditing a communications bill comprising: a.) An audits and error detection module for analyzing information from various data information retrieval units and generating data indicative of whether communications bills are accurate; b.) an electronic billing data information retrieval unit for retrieving information from at least one external input file, wherein said at least one external input file contains communications billing information; c.) a manual entry billing data information retrieval unit for retrieving information containing communications billing information that has been manually entered; d.) at least one interface and formatting module to read billing data from said electronic billing data information retrieval unit or said manual entry billing data information retrieval unit; and e.) an audit report generation module operatively coupled to said audits and error detection module, the audit report generation module generating data indicative of errors and billing discrepancies with the communications bills retrieved by the billing data information retrieval unit or units.
 2. The system of claim 1 wherein the system further comprises a call detail record data information retrieval unit and a means for matching call detail records collected by said call detail record collection module to billing data information contained in the billing data information retrieval unit or units.
 3. The system of claim 1 wherein the system further comprises a SS7 event messaging record data information retrieval unit and a means for matching SS7 event message records collected by said SS7 event messaging record data information retrieval unit to billing data information contained in the billing data information retrieval unit or units.
 4. The system of claim 1 wherein the system further comprises a trouble ticket data information retrieval unit and a means for matching trouble ticket data to billing data information contained in the billing data information retrieval unit or units.
 5. The system of claim 1 wherein the system further comprises a work order data information retrieval unit and a means for matching work order data to billing data information contained in the billing data information retrieval unit or units.
 6. The system of claim 1 wherein the system further comprises an inventory data information retrieval unit and a means for matching inventory data to billing data information contained in the billing data information retrieval unit or units.
 7. The system of claim 1 wherein the system further comprises a dispute processing module.
 8. The system of claim 1 wherein the system further comprises an accounts payable interface module.
 9. The system of claim 1 wherein the system further comprises a data storage and archiving module and a means for retrieving stored data.
 10. The system of claim 1 wherein the audit logic contained in said audit and error detection module can be modified by a user.
 11. The system of claim 1 adapted to automatically e-mail to designated e-mail addresses audit information or hyperlinks to said audit information.
 12. The system of claim 1 adapted to be used through a web browser.
 13. A computer assisted method of auditing a communications bill comprising the steps of: a.) Retrieving billing data information from at least one external input file wherein said at least one external input file contains communications billing information; b.) formatting and storing said billing data information on a data storage device; c.) storing on a computer a set of selectable audit types; d.) selecting one or more selected audit types by inputting appropriate selection data with an input device; e.) performing selected audits using billing data information contained on a data storage device; f.) automatically generating audit reports based on the selected audit types.
 14. The method of claim 13 further including the steps of: a.) Retrieving event records from at least one event record source; b.) formatting and storing said event records on a data storage device; c.) storing on a computer a set of algorithms for comparing said event records to billing data information that has been previously retrieved; d.) selecting one or more algorithms by inputting appropriate selection data with an input device; e.) comparing said event records to said billing data information; and f.) automatically generating reports indicative of the differences between said event records and said billing data information.
 15. The method of claim 13 wherein said event records are Signaling System #7 (SS7) event messaging records.
 16. The method of claim 13 further including the steps of: a.) Retrieving trouble ticket data from at least one source of trouble ticket data; b.) formatting and storing said trouble ticket data on a data storage device; c.) storing on a computer a set of audits for comparing said trouble ticket data to billing data information that has been previously retrieved; d.) selecting one or more audits by inputting appropriate selection data with an input device; e.) performing selected audits using both the trouble ticket data and the billing data information contained on one or more data storage devices; and f.) automatically generating audit reports based on the selected audit types.
 17. The method of claim 13 further including the steps of: a.) Retrieving work order data from at least one source of work data; b.) formatting and storing said work order data on a data storage device; c.) storing on a computer a set of audits for comparing said work order data to billing data information that has been previously retrieved; d.) selecting one or more audits by inputting appropriate selection data with an input device; e.) performing selected audits using both the work order data and the billing data information contained on one or more data storage devices; and f.) automatically generating audit reports based on the selected audit types.
 18. The method of claim 13 further including the steps of: a.) Retrieving inventory data from at least one source of inventory data; b.) formatting and storing said inventory data on a data storage device; c.) storing on a computer a set of audits for comparing said inventory data to billing data information that has been previously retrieved; d.) selecting one or more audits by inputting appropriate selection data with an input device; e.) performing selected audits using both the inventory data and the billing data information contained on one or more data storage devices; and f.) automatically generating audit reports based on the selected audit types.
 19. The method of claim 13 further including the step of: a.) Using the results of the selected audits to begin a dispute process wherein the dispute process comprises notifying the vendor of the error and tracking credits received from the vendor for said error.
 20. The method of claim 13 further including the step of: a.) Providing the results of the audits and the processed billing information to an accounts payable system.
 21. The method of claim 13 further including the step of: a.) sending e-mail notifications to designated e-mail addresses containing audit information or hyperlinks to said audit information.
 22. The method of claim 13 wherein the steps are performed through a web browser. 